Preventing programming errors from occurring when programming flash memory cells

ABSTRACT

Mis-programming of MSB data in flash memory is prevented by using ECC decoding logic on the flash die that error corrects the LSB values prior to the LSB values being used in conjunction with the MSB values to determine the proper reference voltage ranges. Error correcting the LSB page data prior to using it in combination with the MSB page data to determine the reference voltage ranges ensures that the reference voltage ranges will be properly determined and programmed into the flash cells.

CROSS-REFERENCE TO RELATED APPLICATIONS

This nonprovisional application claims priority to provisionalapplication Ser. No. 61/918,778, filed on Dec. 20, 2013, and entitled“PREVENTING PROGRAMMING ERRORS FROM OCCURRING WHEN PROGRAMMING FLASHMEMORY CELLS,” which is incorporated by reference herein in itsentirety.

TECHNICAL FIELD OF INVENTION

The invention relates generally to flash memory and, more specifically,to preventing programming errors from occurring when programming flashmemory cells.

BACKGROUND OF THE INVENTION

A flash memory is a non-volatile electrically erasable data storagedevice that evolved from electrically erasable programmable read-onlymemory (EEPROM). The two main types of flash memory are named after thelogic gates that their storage cells resemble: NAND and NOR. NAND flashmemory is commonly used in solid-state drives, which are supplantingmagnetic disk drives in many applications. A NAND flash memory iscommonly organized as multiple blocks, with each block organized asmultiple pages. Each page comprises multiple cells. Each cell is capableof storing an electric charge. Some cells are used for storing databits, while other cells are used for storing error-correcting code bits.A cell configured to store a single bit is known as a single-level cell(SLC). A cell configured to store two bits is known as a multi-levelcell (MLC). In an MLC cell, one bit is commonly referred to as theleast-significant bit (LSB), and the other as the most-significant bit(MSB). A cell configured to store three bits is known as a triple-levelcell (TLC). Writing data to a flash memory is commonly referred to as“programming” the flash memory, due to the similarity to programming anEEPROM.

The electric charge stored in a cell can be detected in the form of acell voltage. To read an SLC flash memory cell, the flash memorycontroller provides one or more reference voltages (also referred to asread voltages) to the flash memory device. Detection circuitry in theflash memory device will interpret the bit as a “0” if the cell voltageis greater than a reference voltage Vref and will interpret the bit as a“1” if the cell voltage is less than the reference voltage Vref. Thus,an SLC flash memory requires a single reference voltage Vref. Incontrast, an MLC flash memory requires three such reference voltages,and a TLC flash memory requires seven such reference voltages. Thus,reading data from an MLC or TLC flash memory device requires that thecontroller provide multiple reference voltages having optimal valuesthat allow the memory device to correctly detect the stored data values.

Determining or detecting stored data values using controller-providedreference voltages is hampered by undesirable physical non-uniformityacross cells of a device that are inevitably introduced by thefabrication process, as such non-uniformity results in the referencevoltages of different cells that store the same bit value beingsignificantly different from each other. The detection is furtherhampered by target or optimal reference voltages changing over time dueto adverse effects of changes in temperature, interference fromprogramming neighboring cells, and numerous erase-program cycles. Errorsin detecting stored data values are reflected in the performancemeasurement known as bit error rate (BER). The use of error-correctingcodes (ECCs) can improve BER to some extent, but the effectiveness ofECCs diminishes as improved fabrication processes result in smaller cellfeatures.

As illustrated in FIG. 1, an MLC flash memory has four cell voltagedistributions 2, 4, 6 and 8 with four respective mean target cellvoltages Vtarget0 12, Vtarget1 14, Vtarget2 16 and Vtarget3 18. Suchcell voltage distributions commonly overlap each other slightly, butsuch overlap is not shown in FIG. 1 for purposes of clarity. During aread operation, to attempt to characterize or detect the two bits ofcell data (i.e., the LSB and MSB) a flash memory device (not shown) usesthree reference voltages it receives from a flash memory controller (notshown): Vref0 22, Vref1 24 and Vref2 26. More specifically, the flashmemory device compares the cell voltage with Vref1 24 to attempt todetect the LSB. If the flash memory device determines that the cellvoltage is less than Vref1 24, i.e., within a window 28, then the flashmemory device characterizes the LSB as a “1”. If the flash memory devicedetermines that the cell voltage is greater than Vref1 24, i.e., withina window 30, then the flash memory device characterizes the LSB as a“0”.

The flash memory device also compares the cell voltage with Vref0 22 andVref2 26 to attempt to detect the MSB. If the flash memory devicedetermines that the cell voltage is between Vref0 22 and Vref2 26, i.e.,within a window 32, then the flash memory device characterizes the MSBas a “0”. If the flash memory device determines that the cell voltage iseither less than Vref0 22 or greater than Vref2 26, i.e., within awindow 34, then the flash memory device characterizes the MSB as a “1”.

To improve BER beyond what is commonly achievable with hard-decisiondecoded ECCs, flash memory controllers may employ soft-decision decodedECCs, such as low density parity check (LDPC) ECCs. Soft-decisiondecoding is more powerful in correcting errors than hard-decisiondecoding, but soft input information must be provided to the ECCdecoding logic. The ECC decoder soft input information is commonlyprovided in the form of log likelihood ratio (LLR) information.

MLC NAND flash memory is programmed in two stages, namely, a first stageduring which LSB page programming is performed, and a second stageduring which MSB page programming is performed. The first stage includesthe following: (1) the flash memory controller sends LSB data to flashmemory; (2) the flash memory loads the LSB data into an LSB page bufferportion of the flash memory; and (3) the flash memory uses the LSB datato program the corresponding LSB page of the flash memory. The secondstage includes the following: (1) the flash memory controller sends theMSB data to be programmed to flash memory; (2) the flash memory loadsthe MSB data into an MSB page buffer portion of the flash memory; (3)logic of the flash memory reads the LSB page of the corresponding flashcells and loads the read LSB data into the LSB page buffer portion; (4)the logic uses the MSB and LSB value pairs held in the flash page bufferto determine the target reference voltage ranges to be programmed forthe corresponding flash cells; and (5) the logic programs the targetreference voltage ranges into the flash memory.

As flash memory technology improves, the sizes of the flash dies scaledown, which results in the distance between neighboring flash cellsbecoming smaller. Because of the nearness of neighboring flash cells toone another, the programming of one flash cell can affect the chargesstored on nearby flash cells, which contributes to the potentially noisyand unreliable nature of flash cells. Consequently, there can be errorsin the LSB page data read out of the corresponding flash cells. Becausethe LSB page data read out of the flash cells is used in combinationwith the MSB page data to determine the target reference voltage rangesfor the corresponding cells, such errors will typically cause the targetreference voltage ranges to be incorrectly determined. This can causethe flash cells to be mis-programmed to improper reference voltageranges when performing MSB page programming. The improper referencevoltage ranges often will be far away from the borders of flash neighborstates and could provide incorrect, but highly confident, softinformation. This, in turn, can significantly degrade the errorcorrection performance of soft-decision decoding, such as LDPC decoding.

FIG. 2 illustrates cell voltage distributions and target referencevoltage ranges for different LSB and MSB states and demonstrates themanner in which the reference voltage ranges are selected based on thevalues of the MSB and LSB pair. Cell voltage distribution 42 representsthe LSB and MSB erased program state. Cell distributions 43 and 44represent LSB “1” and “0” programmed states, respectively. Celldistributions 45, 46, 47, and 48 represent MSB programmed states of “1,”“0,” “0,” and “1,” respectively.

If the MSB and LSB values of the MSB, LSB pair contained in the flashpage buffer are both “1,” then the reference voltage range that will beprogrammed into the flash memory for the corresponding flash cells isselected to be range A, which is the range of reference voltages that isless than Vref0. If the MSB and LSB values of the MSB, LSB paircontained in the flash page buffer are “1” and “0,” respectively, thenthe reference voltage range that will be programmed into the flashmemory device for the corresponding flash cells is selected to be rangeD, which is the range of reference voltages that is greater than Vref2.If the MSB and LSB values of the MSB, LSB pair contained in the flashpage buffer are “0” and “1,” respectively, then the reference voltagerange that will be programmed into the flash memory device for thecorresponding flash cells is selected to be range B, which is the rangeof reference voltages that is greater than Vref0 and less than Vref1.

As can be seen from the above, if the LSB values that are read from theflash memory cells are inaccurate, which is possible for the reasonsdescribed above, then the reference voltage ranges will likely bemis-programmed. Accordingly, a need exists for a way to ensure that thereference voltage ranges are correctly determined and programmed.

SUMMARY OF THE INVENTION

Embodiments of the invention relate to a data storage system, a flashmemory IC for use in the data storage system, and methods used thereinfor preventing programming errors from occurring when programming flashmemory. In accordance with an illustrative embodiment, the data storagesystem comprises a host system and a solid state drive (SSD) that areinterfaced with one another. The SSD includes an SSD controller and atleast one nonvolatile memory (NVM). The SSD controller includes at leastone SSD processor, a tier 1 error-correcting ECC encoder/decoder, and atier 2 ECC encoder/decoder. The NVM includes at least a first flashmemory having a plurality of flash memory cells, reference voltage rangedetermination logic and tier 2 ECC decoding logic. The SSD controllerreceives write data from the host system to be programmed into flashcells of the NVM. The write data comprises at least a first MSB page ofdata and at least a first LSB page of data. The tier 1 ECCencoder/decoder performs tier 1 ECC encoding of the first LSB page ofdata to produce a tier 1-encoded first LSB page of data. The tier 2 ECCencoder/decoder performs tier 2 ECC encoding of the tier 1-encoded firstLSB page of data to produce a tier 1/tier 2-encoded first LSB page data.The SSD controller sends the tier 1/tier 2-encoded first LSB page ofdata to the first flash memory. The tier 1 ECC encoding/decoding logicperforms tier 1 ECC encoding of the first MSB page of data to produce atier 1-encoded first MSB page of data. The SSD controller sends the tier1-encoded first MSB page of data to the first flash memory. The tier 1ECC encoding and the tier 2 encoding are different types of encoding.The tier 2 decoding logic of the first flash memory is adapted toperform tier 2 decoding of LSB page data in the first flash memory. Thetier 2-decoded first LSB page of data is subsequently used inconjunction with the tier 1-encoded MSB page data in the first flashmemory to determine reference voltage ranges for the flash memory cells

In accordance with an illustrative embodiment, the flash memory IC diecomprises a plurality of flash memory cells for storing data and ECCdecoding logic. The flash memory IC die is configured to receive writedata from an interface that interfaces an SSD controller with the firstflash memory IC die. The received write data comprises at least a firstLSB page of data and at least a first MSB page of data. The first LSBpage of data is encoded with a tier 1 ECC encoding and with a tier 2 ECCencoding. The first MSB page of data is encoded with the tier 1encoding. The flash memory IC die programs the first LSB page of data toa first LSB page of the flash memory cells. Prior to the first flashmemory IC die programming the first MSB page of data to a first MSB pageof the flash memory cells, the first flash memory IC die causes theencoded first LSB page of data to be read from the first LSB page of theflash memory cells and sent to the ECC decoding logic. The ECC decodinglogic performs tier 2 ECC decoding of the encoded LSB page data toproduce a tier 2-decoded first LSB page of data that is subsequentlyused in conjunction with the tier 1-encoded MSB page data to determinereference voltage ranges for the flash memory cells.

These and other features and advantages of the invention will becomeapparent from the following description, drawings and claims.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a plot of cell voltage distributions in a flash memory device,as known in the art, and demonstrates the known manner in which LSB andMSB values are determined.

FIG. 2 is a plot of cell voltage distributions in a flash memory device,as known in the art, and demonstrates the manner in which LSB and MSBvalue pairs are used to determine the reference voltage ranges.

FIG. 3 illustrates a block diagram of a storage system in accordancewith an illustrative embodiment that includes one or more instances ofan SSD device that is suitable for implementing the invention.

FIG. 4 illustrates a block diagram of an illustrative embodiment of oneof the SSDs shown in FIG. 3 including the SSD controller shown in FIG. 3that performs flash cell programming in a way that ensures thatprogramming errors do not occur when programming the reference voltageranges of the flash cells.

FIG. 5 illustrates a block diagram of a plurality of flash cellsdisposed in a portion of one of the flash dies shown in FIG. 4.

FIG. 6 illustrates a block diagram of a portion of one of the flash diesshown in FIG. 4 that includes reference voltage range determinationlogic, a flash memory buffer and tier 2 ECC decoding logic.

FIGS. 7A-7C illustrate an LSB page data frame before and after beingconcatenated with tier 1 and tier 2 parity bits.

FIGS. 8A-8C illustrate an MSB page data frame before and after beingconcatenated with tier 1 parity bits and other data bits.

FIG. 9 illustrates a flow diagram that represents the method inaccordance with an illustrative embodiment for preventing errors fromoccurring when determining reference voltage ranges for flash memorycells of a flash die.

DETAILED DESCRIPTION OF AN ILLUSTRATIVE EMBODIMENT

In accordance with exemplary, or illustrative, embodiments, the LSBvalues that are used in conjunction with the MSB values to determine theproper reference voltage ranges are error corrected by ECC decodinglogic inside of the flash memory before being used in conjunction withthe MSB values to determine the proper reference voltage ranges. Errorcorrecting the LSB page data prior to using it in combination with theMSB page data to determine the reference voltage ranges ensures that thereference voltage ranges will be properly determined and programmed intothe flash cells.

Embodiments of the invention can be implemented in a number of ways, andtherefore a few illustrative embodiments are described below withreference to FIGS. 3-9, in which like reference numerals in the figuresidentify like features, components or elements. Before describingspecific embodiments for ensuring that programming errors do not occurwhen programming the reference voltage ranges of the flash cells, thecomponents of the storage system in accordance with an illustrativeembodiment and the functions that they perform will be generallydescribed with reference to FIGS. 3 and 4.

FIG. 3 illustrates a block diagram of a storage system in accordancewith an illustrative embodiment that includes one or more instances of asolid state drive (SSD) 101 that implements the invention. The SSD 101includes an SSD controller 100 coupled to NVM 199 via device interfaces190. As will be described below in more detail with reference to FIG. 4,the NVM 199 comprises one or more flash memory dies, each of whichcomprises a plurality of flash cells. The storage system may include,for example, a host system 102, a single SSD 101 coupled directly to thehost system 102, a plurality of SSDs 101 each respectively coupleddirectly to the host system 102 via respective external interfaces, orone or more SSDs 101 coupled indirectly to a host system 102 via variousinterconnection elements. As an exemplary embodiment of a single SSD 101coupled directly to the host system 102, one instance of SSD 101 iscoupled directly to host system 102 via external interfaces 110 (e.g.,switch/fabric/intermediate controller 103 is omitted, bypassed, orpassed-through).

As an exemplary embodiment of a plurality of SSDs 101 being coupleddirectly to the host system 102 via respective external interfaces, eachof a plurality of instances of SSD 101 is respectively coupled directlyto host system 102 via a respective instance of external interfaces 110(e.g., switch/fabric/intermediate controller 103 is omitted, bypassed,or passed-through). As an exemplary embodiment of one or more SSDs 101coupled indirectly to host system 102 via various interconnectionelements, each of one or more instances of SSD 101 is respectivelycoupled indirectly to host system 102 via a respective instance ofexternal interfaces 110 coupled to switch/fabric/intermediate controller103, and intermediate interfaces 104 coupled to host system 102.

The host system 102 includes one or more processors, such as, forexample, one or more microprocessors and/or microcontrollers operatingas a central processing unit (CPU) 102 a, and a host memory device 102 bfor storing instructions and data used by the host CPU 102 a. Hostsystem 102 is enabled or configured via the host CPU 102 a to executevarious elements of host software 115, such as various combinations ofoperating system (OS) 105, driver 107, application 109, and multi-devicemanagement software 114. The host software 115 is stored in a memorydevice 102 b of the host system 102 and is executed by the host CPU 102a. Dotted-arrow 107D is representative of host software

I/O device communication, e.g., data sent/received to/from one or moreof the instances of SSD 101 and from/to any one or more of OS 105 viadriver 107, driver 107, and application 109, either via driver 107, ordirectly as a VF.

OS 105 includes and/or is enabled or configured to operate with drivers(illustrated conceptually by driver 107) for interfacing with the SSD.Various versions of Windows (e.g., 95, 98, ME, NT, XP, 2000, Server,Vista, and 7), various versions of Linux (e.g., Red Hat, Debian, andUbuntu), and various versions of MacOS (e.g., 8, 9 and X) are examplesof OS 105. In various embodiments, the drivers are standard and/orgeneric drivers (sometimes termed “shrink-wrapped” or “pre-installed”)operable with a standard interface and/or protocol such as SATA, AHCI,or NVM Express, or are optionally customized and/or vendor specific toenable use of commands specific to SSD 101.

Some drives and/or drivers have pass-through modes to enableapplication-level programs, such as application 109 via optimized NANDAccess (sometimes termed ONA) or direct NAND Access (sometimes termedDNA) techniques, to communicate commands directly to SSD 101, enabling acustomized application to use commands specific to SSD 101 even with ageneric driver. ONA techniques include one or more of: use ofnon-standard modifiers (hints); use of vendor-specific commands;communication of non-standard statistics, such as actual NVM usageaccording to compressibility; and other techniques. DNA techniquesinclude one or more of: use of non-standard commands or vendor-specificproviding unmapped read, write, and/or erase access to the NVM; use ofnon-standard or vendor-specific commands providing more direct access tothe NVM, such as by bypassing formatting of data that the I/O devicewould otherwise do; and other techniques. Examples of the driver are adriver without ONA or DNA support, an ONA-enabled driver, a DNA-enableddriver, and an ONA/DNA-enabled driver. Further examples of the driverare a vendor-provided, vendor-developed, and/or vendor-enhanced driver,and a client-provided, client-developed, and/or client-enhanced driver.

Examples of the application-level programs are an application withoutONA or DNA support, an ONA-enabled application, a DNA-enabledapplication, and an ONA/DNA-enabled application. Dotted-arrow 109D isrepresentative of application I/O device communication (e.g. bypass viaa driver or bypass via a VF for an application), e.g. an ONA-enabledapplication and an ONA-enabled driver communicating with an SSD, such aswithout the application using the OS as an intermediary. Dotted-arrow109V is representative of application I/O device communication (e.g.bypass via a VF for an application), e.g. a DNA-enabled application anda DNA-enabled driver communicating with an SSD, such as without theapplication using the OS or the driver as intermediaries.

Some of the embodiments that include switch/fabric/intermediatecontroller 103 also include card memory 112C coupled via memoryinterface 180 and accessible by the SSDs 101. In various embodiments,one or more of the SSDs 101, the switch/fabric/intermediate controller103, and/or the card memory 112C are included on a physicallyidentifiable module, card, or pluggable element (e.g., I/O Card 116). Insome embodiments, SSD 101 (or variations thereof) corresponds to a SASdrive or a SATA drive that is coupled to an initiator operating as hostsystem 102.

In some embodiments lacking the switch/fabric/intermediate controller,the SSD 101 is coupled to the host system 102 directly via externalinterfaces 110. In various embodiments, SSD Controller 100 is coupled tothe host system 102 via one or more intermediate levels of othercontrollers, such as a RAID controller. In some embodiments, SSD 101 (orvariations thereof) corresponds to a SAS drive or a SATA drive andswitch/fabric/intermediate controller 103 corresponds to an expanderthat is in turn coupled to an initiator, or alternativelyswitch/fabric/intermediate controller 103 corresponds to a bridge thatis indirectly coupled to an initiator via an expander. In someembodiments, switch/fabric/intermediate controller 103 includes one ormore PCIe switches and/or fabrics.

In various embodiments, such as some of the embodiments where hostsystem 102 is a computing host (e.g., a computer, a workstationcomputer, a server computer, a storage server, a SAN, a NAS device, aDAS device, a storage appliance, a PC, a laptop computer, a notebookcomputer, and/or a netbook computer), the computing host is optionallyenabled to communicate (e.g., via optional I/O & StorageDevices/Resources 117 and optional LAN/WAN 119) with one or more localand/or remote servers (e.g., optional servers 118). The communicationenables, for example, local and/or remote access, management, and/orusage of any one or more of SSD 101 elements. In some embodiments, thecommunication is wholly or partially via Ethernet. In some embodiments,the communication is wholly or partially via Fibre Channel. LAN/WAN 119is representative, in various embodiments, of one or more Local and/orWide Area Networks, such as any one or more of a network in a serverfarm, a network coupling server farms, a metro-area network, and theInternet.

In various embodiments, an SSD controller and/or a computing-host flashmemory controller in combination with one or more NVMs are implementedas a non-volatile storage component, such as a USB storage component, aCF storage component, a MultiMediaCard (MMC) storage component, an eMMCstorage component, a Thunderbolt storage component, a UFS storagecomponent, an SD storage component, a memory stick storage component,and an xD-picture card storage component.

In various embodiments, all or any portions of an SSD controller (or acomputing-host flash memory controller), or functions thereof, areimplemented in a host that the controller is to be coupled with (e.g.,host system 102). In various embodiments, all or any portions of an SSDcontroller (or a computing-host flash memory controller), or functionsthereof, are implemented via hardware (e.g., logic circuitry), softwareand/or firmware (e.g., driver software or SSD control firmware), or anycombination thereof.

FIG. 4 illustrates a block diagram of an illustrative embodiment of oneof the SSDs 101 shown in FIG. 3 including the SSD controller 100 shownin FIG. 3 that performs flash cell programming in a way that ensuresthat programming errors do not occur when programming the referencevoltage ranges of the flash cells. Prior to describing an illustrativeembodiment of the manner in which the SSD controller 100 performs flashcell programming, the configuration of the SSD controller 100 that issuitable for performing the methods will be described with reference toFIG. 4.

SSD controller 100 is communicatively coupled via one or more externalinterfaces 110 to the host system 102 (FIG. 3). According to variousembodiments, external interfaces 110 are one or more of: a SATAinterface; a SAS interface; a PCIe interface; a Fibre Channel interface;an ethernet interface (such as 10 Gigabit Ethernet); a non-standardversion of any of the preceding interfaces; a custom interface; or anyother type of interface used to interconnect storage and/orcommunications and/or computing devices. For example, in someembodiments, SSD controller 100 includes a SATA interface and a PCIeinterface.

SSD controller 100 is further communicatively coupled via one or moredevice interfaces 190 to NVM 199, which includes one or more flashdevices 192. According to various illustrative embodiments, deviceinterfaces 190 are one or more of: an asynchronous interface; asynchronous interface; a single-data-rate (SDR) interface; adouble-data-rate (DDR) interface; a DRAM-compatible DDR or DDR2synchronous interface; an Open NAND Flash Interface (ONFI) compatibleinterface, such as an ONFI 2.2 or ONFI 3.0 compatible interface; aToggle-mode compatible flash interface; a non-standard version of any ofthe preceding interfaces; a custom interface; or any other type ofinterface used to connect to storage devices.

Each flash device 192 includes one or more individual flash dies 194.According to type of a particular one of flash devices 192, a pluralityof the flash dies 194 in the particular flash device 192 are optionallyand/or selectively accessible in parallel. Flash device 192 is merelyrepresentative of one type of storage device enabled to communicativelycouple to SSD controller 100. In various embodiments, any type ofstorage device is usable, such as an SLC NAND flash memory, MLC NANDflash memory, NOR flash memory, flash memory using polysilicon orsilicon nitride technology-based charge storage cells, two- orthree-dimensional technology-based flash memory, read-only memory,static random access memory, dynamic random access memory, ferromagneticmemory, phase-change memory, racetrack memory, ReRAM, or any other typeof memory device or storage medium.

According to various embodiments, device interfaces 190 are organizedas: one or more busses with one or more of flash device 192 per bus; oneor more groups of busses with one or more of flash device 192 per bus,where busses in a group are generally accessed in parallel; or any otherorganization of one or more of flash device 192 onto device interfaces190.

The SSD controller 100 typically, but not necessarily, has one or moremodules, such as, for example, host interfaces module 111, dataprocessing module 121, buffer module 131, map module 141, recyclermodule 151, ECC module 161, device interface logic module 191, and CPU171. The specific modules and interconnections illustrated in FIG. 4 aremerely representative of one embodiment, and many arrangements andinterconnections of some or all of the modules, as well as additionalmodules not illustrated, are possible, and fewer than all of the modulesshown in FIG. 4 may be included in the SSD controller 100. In a firstexample, in some embodiments, there are two or more host interfaces 111to provide dual-porting. In a second example, in some embodiments, dataprocessing module 121 and/or ECC module 161 are combined with buffermodule 131. In a third example, in some embodiments, host interfacesmodule 111 is directly coupled to buffer module 131, and data processingmodule 121 optionally and/or selectively operates on data stored inbuffer module 131. In a fourth example, in some embodiments, deviceinterface logic module 191 is directly coupled to buffer module 131, andECC module 161 optionally and/or selectively operates on data stored inbuffer module 131.

Host interfaces module 111 sends and receives commands and/or data viaexternal interfaces 110. For example, the commands include a readcommand specifying an address (such as a logical block address (LBA))and an amount of data (such as a number of LBA quanta, e.g., sectors) toread; in response the SSD 101 provides read status and/or read data. Asanother example, the commands include a write command specifying anaddress (such as an LBA) and an amount of data (such as a number of LBAquanta, e.g., sectors) to write; in response the SSD 101 provides writestatus and/or requests write data and optionally subsequently provideswrite status. For yet another example, the commands include ade-allocation command (e.g., a trim command) specifying one or moreaddresses (such as one or more LBAs) that no longer need be allocated.

According to various embodiments, one or more of: Data processing module121 optionally and/or selectively processes some or all data sentbetween buffer module 131 and external interfaces 110; and dataprocessing module 121 optionally and/or selectively processes datastored in buffer module 131. In some embodiments, data processing module121 uses one or more engines 123 to perform one or more of: formatting;reformatting; transcoding; and any other data processing and/ormanipulation task.

Buffer module 131, which is optional, stores data sent to/from externalinterfaces 110 from/to device interfaces 190. In some embodiments,buffer module 131 additionally stores system data, such as some or allmap tables, used by SSD controller 100 to manage one or more of theflash devices 192. Buffer module 131 is typically a portion of the localmemory of the SSD controller 100 that has been allocated for use astemporary storage for storing MSB and LSB page data to be written toflash memory cells of the flash die 194. The buffer module 131typically, but not necessarily, also includes a direct memory access(DMA) engine (not shown) that is used to control movement of data toand/or from the buffer module 131 and ECC-X engine (not shown) that isused to provide higher-level error correction and/or redundancyfunctions.

ECC module 161 processes some or all data sent between buffer module 131and device interfaces 190. ECC module 161 optionally and/or selectivelyprocesses data stored in buffer module 131. In some embodiments, ECCmodule 161 is used to provide lower-level error correction and/orredundancy functions in accordance with one or more ECC techniques. Insome embodiments, ECC module 161 implements one or more of: a CRC code;a Hamming code; an RS code; a BCH code; an LDPC code; a Viterbi code; atrellis code; a hard-decision code; a soft-decision code; anerasure-based code; any error detecting and/or correcting code; and anycombination of the preceding.

ECC module 161 includes one or more ECC encoders for performing ECCencoding and one or more ECC decoders for performing ECC decoding. Inaccordance with an illustrative embodiment, the ECC module 161 includestwo tiers of encoding/decoding logic, namely, a tier 1 encoding/decoder161 a and a tier 2 encoder/decoder 161 b. The tier 1 encoder/decoder 161a performs a stronger, or more robust, level of ECC encoding/decodingthan the level of ECC encoding/decoding performed by the tier 2encoding/decoding logic 161 b. For example, the tier 1 encoder/decoder161 a may use LDPC codes whereas the tier 2 encoder/decoder 161 b mayuse BCH codes. The tier 1 encoding/decoding is typically soft-decisionECC encoding/decoding, whereas the tier 2 encoding/decoding is typicallya hard-decision ECC encoding/decoding. The reasons for using thesedifferent levels of ECC encoding/decoding is described below in detail.The invention is not limited with respect to the types of soft- andhard-decision ECC encoding/decoding techniques that are used as the tier1 and tier 2 ECC encoding/decoding techniques, respectively. As will beunderstood by those of skill in the art in view of the description beingprovided herein, a variety of soft- and hard-decision ECCencoding/decoding techniques are suitable for use with the invention asthe tier 1 and tier 2 ECC encoding/decoding techniques, respectively.Because such techniques are well known in the art, they will not bedescribed herein in detail.

Device interface logic module 191 controls instances of flash device 192via device interfaces 190. Device interface logic module 191 is enabledto send data to/from the instances of flash device 192 according to aprotocol of flash device 192. Device interface logic module 191typically includes scheduling logic 193 that selectively sequencecontrols instances of flash device 192 via device interfaces 190. Forexample, in some embodiments, scheduling logic 193 is enabled to queueoperations to the instances of flash device 192, and to selectively sendthe operations to individual ones of the instances of flash device 192(or flash die 194) as individual ones of the instances of flash device192 (or flash die 194) become available.

Map module 141 converts between data addressing used on externalinterfaces 110 and data addressing used on device interfaces 190, usingtable 143 to map external data addresses to locations in NVM 199. Forexample, in some embodiments, map module 141 converts LBAs used onexternal interfaces 110 to block and/or page addresses targeting one ormore flash die 194, via mapping provided by table 143. In someembodiments, map module 141 uses table 143 to perform and/or to look uptranslations between addresses used on external interfaces 110 and dataaddressing used on device interfaces 190. According to variousembodiments, table 143 is one or more of: a one-level map; a two-levelmap; a multi-level map; a map cache; a compressed map; any type ofmapping from one address space to another; and any combination of theforegoing. According to various embodiments, table 143 includes one ormore of: static random access memory; dynamic random access memory; NVM(such as flash memory); cache memory; on-chip memory; off-chip memory;and any combination of the foregoing.

In some embodiments, recycler module 151 performs garbage collection.For example, in some embodiments, instances of flash device 192 containblocks that must be erased before the blocks are re-writeable. Recyclermodule 151 is enabled to determine which portions of the instances offlash device 192 are actively in use (e.g., allocated instead ofde-allocated), such as by scanning a map maintained by map module 141,and to make unused (e.g., de-allocated) portions of the instances offlash device 192 available for writing by erasing them. In furtherembodiments, recycler module 151 is enabled to move data stored withininstances of flash device 192 to make larger contiguous portions of theinstances of flash device 192 available for writing.

In some embodiments, instances of flash device 192 are selectivelyand/or dynamically configured, managed, and/or used to have one or morebands for storing data of different types and/or properties. A number,arrangement, size, and type of the bands are dynamically changeable. Forexample, data from a computing host is written into a hot (active) band,while data from recycler module 151 is written into a cold (less active)band. In some usage scenarios, if the computing host writes a long,sequential stream, then a size of the hot band grows, whereas if thecomputing host does random writes or few writes, then a size of the coldband grows.

CPU 171 controls various portions of SSD controller 100. CPU module 171typically includes CPU Core 172, which is, according to variousembodiments, one or more single-core or multi-core processors. Theindividual processor cores in CPU core 172 are, in some embodiments,multi-threaded. CPU core 172 includes instruction and/or data cachesand/or memories. For example, the instruction memory containsinstructions to enable CPU core 172 to execute programs (e.g. softwaresometimes called firmware) to control SSD Controller 100. In someembodiments, some or all of the firmware executed by CPU core 172 isstored on instances of flash device 192.

In various embodiments, CPU 171 further includes: command managementlogic 173 for tracking and controlling commands received via externalinterfaces 110 while the commands are in progress; buffer managementlogic 175 for controlling allocation and use of buffer module 131;translation Management logic 177 for controlling map module 141;coherency management module 179 for controlling consistency of dataaddressing and for avoiding conflicts such as between external dataaccesses and recycle data accesses; device management logic 181 forcontrolling device interface logic 191; identity management logic 182for controlling modification and communication of identity information,and optionally other management units. None, any, or all of themanagement functions performed by CPU 171 are, according to variousembodiments, controlled and/or managed by hardware, by software (such asfirmware executing on CPU core 172 or on host system 102 (FIG. 3)connected via external interfaces 110), or any combination thereof.

In various embodiments, all or any portions of an SSD Controller 100 areimplemented on a single IC, a single die of a multi-die IC, a pluralityof dice of a multi-die IC, or a plurality of ICs. For example, buffermodule 131 may be implemented on a same die as other elements of SSDcontroller 100. As another example, buffer module 131 may be implementedon a different die than other elements of SSD controller 100. The SSDcontroller 100 and one or more of the flash devices 192 may beimplemented on the same die, although they are typically implemented onseparate dies.

As described above in the Background of the Invention, flash memory istypically programmed in two stages, namely, a first stage during whichLSB page programming is performed and a second stage during which MSBpage programming is performed. As also described above, during thesecond stage, errors in the LSB page data read out of the flash cellswill typically cause the target reference voltage ranges to beincorrectly determined, and therefore mis-programmed. Because the timeinterval between LSB page programming and MSB page programming istypically short, the LSB page data does not contain retention errors,but may contain errors caused by other factors (i.e., program, eraseand/or read errors). However, such errors can be easily corrected byusing known hard-decision (i.e., relatively weak) ECC decodingtechniques, which can be relatively easily and inexpensively implementedon a flash die 194. Because the SSD controller 100 should be capable ofhandling all types of errors (i.e., retention, program, erase and/orread errors), soft-decision (i.e., relatively strong) ECCencoding/decoding techniques are implemented in the SSD controller 100by the ECC module 161 for all data that is written to and read from theflash dies 194, as will be described below in detail.

In accordance with an illustrative embodiment, tier 2 ECC decoding logicis implemented on the flash die. During the MSB page data programmingstage, the associated LSB page data is read from the flash cells and iserror corrected by the tier 2 ECC decoding logic of the flash die. Theerror-corrected LSB page data is then used in conjunction with the MSBpage data in the known manner to determine the proper reference voltageranges to be programmed for the flash cells. The manner in which the MSBpage data programming stage has been altered to perform the ECC decodingprocess on the flash die 194 to ensure that the LSB data that is used indetermining the reference voltage values does not contain errors willnow be described with reference to FIGS. 3-9.

FIG. 5 illustrates a block diagram of a plurality of flash cells 195disposed in a portion 194 a of one of the flash dies 194 shown in FIG.4. A plurality of word lines 196 a-196 d and bit lines 197 are used toaddress LSB and MSB pages of the flash cells 195 (FIG. 5). An example ofthe manner in which the LSB and MSB pages are programmed is providedbelow in conjunction with a description of the manner in which the MSBpage data programming stage has been altered to perform the ECC decodingprocess on the flash die 194.

FIG. 6 illustrates a block diagram of a portion of one of the flash dies194 that includes reference voltage determination logic 200 fordetermining the reference voltage ranges for the flash cells 195, aflash memory buffer 201 for holding MSB data and LSB data to be writtento the flash cells 195, and tier 2 ECC decoding logic 210 for performingtier 2 decoding of LSB page data to be used in determining the referencevoltage ranges for the flash cells 195. The logic 200 and 210 aretypically state machines, but could be some other type of logic, such asone or more processors, for example. The invention is not limited withrespect to the manner in which the logic 200 and 210 are implemented inthe flash die 194. The manner in which the reference voltagedetermination logic 200, the flash memory buffer 201 and the tier 2 ECCdecoding logic 210 operate is described below in conjunction with adescription of the manner in which the MSB page data programming stagehas been altered to perform the ECC decoding process on the flash die194.

FIGS. 7A-7C illustrate LSB data frames before and after beingconcatenated with tier 1 and tier 2 parity bits. FIGS. 8A-8C illustrateLSB data frames before and after being concatenated with tier 1 paritybits and other data. An example of the manner in which the data isencoded/decoded is described below in conjunction with a description ofthe manner in which the MSB page data programming stage has been alteredto perform the ECC decoding process on the flash die 194.

In accordance with an illustrative embodiment, the following processoccurs when writing data to the flash die 194: (1) MSB and LSB page datato be written to flash memory is received in the SSD controller 100(FIG. 3) from the host system 102 (FIG. 3). For exemplary purposes, itwill be assumed that the SSD controller 100 temporarily places the LSBpage data in buffer 131 (FIG. 4), although the buffer 131 and thebuffering step are optional because some SSD controllers do not includesuch buffers. The MSB and LSB page data to be written is loaded into thebuffer 131 (FIG. 4) of the SSD controller 100; (2) the LSB page data(FIG. 7A) held in the buffer 131 (FIG. 4) is subjected to tier 1 (i.e.,relatively strong) ECC encoding (FIG. 7B); (3) the tier 1-encoded LSBpage data (FIG. 7B) is then subjected to tier 2 (i.e., relatively weak)ECC encoding (FIG. 7C); (4) the tier 1/tier 2-encoded LSB page data(FIG. 7C) is sent to the flash die 194 (FIG. 4), which loads it into theLSB page buffer portion 201 b (FIG. 6) of the flash memory buffer 201;(5) the tier 1/tier 2-encoded LSB page data contained in the LSB pagebuffer portion 201 b (FIG. 6) is written, or programmed, to thecorresponding LSB page of the flash cells 195 (FIG. 5); (6) the MSB pagedata (FIG. 8A) contained in the buffer 131 (FIG. 4) is subjected to tier1 ECC encoding; (7) the tier 1-encoded MSB page data (FIG. 8B), withother data bits concatenated to it (FIG. 8C) to make it the same size asthe concatenated LSB frame shown in FIG. 7C, is then sent to the flashdie 194, which loads the tier 1-encoded MSB page data into the MSB pagebuffer portion 201 a (FIG. 6); (8) the tier 1/tier 2-encoded LSB pagedata is read from the LSB page of flash memory cells 195 (FIG. 5) andsent to tier 2 ECC decoding logic 210 (FIG. 6) of the flash die 194; (9)the tier 2 ECC decoding logic 210 (FIG. 6) of the flash die 194 (FIGS. 4and 5) performs tier 2 ECC decoding to produce an error-corrected tier1-encoded LSB page data and loads the error-corrected tier 1-encoded LSBpage data into the LSB page buffer portion 201 b; (10) theerror-corrected tier 1-encoded LSB page data and the tier 1-encoded MSBpage data contained in the LSB page buffer 201 b and the MSB page bufferportion 201 a, respectively, are used by the reference voltagedetermination logic 200 (FIG. 6) of the flash die 194 to determine theproper reference voltage ranges for the corresponding flash cells 195(FIG. 5) of the die 194; and (11) the reference voltage determinationlogic 200 (FIG. 6) programs the corresponding flash cells 195 (FIG. 5)to the proper reference voltage ranges.

An example of the manner in which steps (1)-(11) are performed duringLSB and MSB page programming in accordance with an illustrativeembodiment will now be described. The SSD controller 100 receives datato be written to the NVM 199 from the host system 102. For examplepurposes, it will be assumed that eight pages (LSB pages 0, 1, 3, and 5and MSB pages 2, 4, 6, and 8) of data are to be written to the flash dieportion 194 a (FIG. 5). The eight pages of data are received in the SSDcontroller 100 from the host system 102. The invention is not limitedwith respect to the size of the data frames that are transferred fromthe host system 102 to the SSD controller 100. It will also be assumedthat the data is temporarily stored in the buffer 131, although thebuffer 131 and the buffering step are optional.

The SSD controller 100 loads LSB page 0, LSB page 1, MSB page 2 and MSBpage 4 data into buffer 131. The ECC module 161 uses the tier 1encoder/decoder 161 a and the tier 2 encoded/decoder 161 b to performtier 1 and tier 2 ECC encoding, respectively, on the LSB page 0 datasuch that the LSB page 0 data has the configuration shown in FIG. 7C.The SSD controller 100 sends the tier 1/tier 2-encoded LSB page 0 datato the flash die 194, which loads the LSB page 0 data into the LSB pagebuffer portion 201 b (FIG. 6) of flash die 194. In a typicalconfiguration of the flash die 194, the MSB and LSB page buffer portions201 a and 201 b (FIG. 6), respectively, each have a capacity for holdinga single page of MSB and LSB data, respectively, although the inventionis not limited with respect to the storage capacity of buffer portions201 a and 201 b. Logic (not shown) inside of the flash die 194 thenwrites the tier 1/tier 2-encoded LSB page 0 data held in LSB page bufferportion 201 b to the corresponding flash cells 195 (FIG. 5) connected toword line 196 a (FIG. 5).

The ECC module 161 uses the tier 1 encoder/decoder 161 a and the tier 2encoded/decoder 161 b to perform tier 1 and tier 2 ECC encoding,respectively, on the LSB page 1 data such that the LSB page 1 data hasthe configuration shown in FIG. 7C. The SSD controller 100 sends thetier 1/tier 2-encoded LSB page 1 data to the flash die 194, which loadsthe LSB page 1 data into the LSB page buffer portion 201 b (FIG. 6) offlash die 194, thereby overwriting the LSB page 0 data. Logic (notshown) inside of the flash die 194 then writes the LSB page 1 data tocorresponding flash cells 195 connected to word line 196 b (FIG. 5).

The ECC module 161 (FIG. 4) uses the tier 1 encoder/decoder 161 a toperform tier 1 ECC encoding on the MSB page 2 data such that the MSBpage 2 data has the configuration shown in FIG. 8B. Additional data bitsare added to the MSB page 2 data such that it has the configurationshown in FIG. 8C. The SSD controller 100 sends the tier 1-encoded MSBpage 2 data to the flash die 194, which loads the tier-1-encoded MSBpage 2 data into the MSB page buffer portion 201 a (FIG. 6) of flash die194. The tier 2 decoding logic 210 reads the tier 1/tier 2-encoded LSBpage 0 data from the LSB page of flash cells 195 (FIG. 5), performs tier2 ECC decoding on the LSB page 0 data to produce error-corrected tier1-encoded LSB page 0 data, and loads the error-corrected tier 1-encodedLSB page 0 data into the LSB page buffer portion 201 b (FIG. 6). Thereference voltage determination logic 200 (FIG. 6) then uses the tier1-encoded MSB page 2 data and the error-corrected tier 1-encoded LSBpage 0 data contained in the MSB and LSB page buffer portions 201 a and201 b, respectively, to determine the proper reference voltage ranges tobe programmed for the flash cells 195 connected to word line 196 a (FIG.5). Because the manner in which the LSB and MSB data pair is used todetermine the proper reference voltage ranges has been described abovewith reference to FIG. 2, it will not be described again herein in theinterest of brevity.

The ECC module 161 (FIG. 4) uses the tier 1 encoder/decoder 161 a toperform tier 1 ECC encoding on the MSB page 4 data. The SSD controller100 then sends the tier 1-encoded MSB page 4 data (FIG. 8C) to the flashdie 194, which loads the encoded MSB page 4 data into the MSB pagebuffer portion 201 a (FIG. 6). The tier 2 decoding logic 210 reads thetier 1/tier 2-encoded LSB page 1 data from the LSB page of flash cells195 (FIG. 5), performs tier 2 ECC decoding on the LSB page 1 data tocorrect errors in the LSB page 1 data, and loads the error-corrected LSBpage 1 data into the LSB page buffer portion 201 b (FIG. 6). Thereference voltage determination logic 200 (FIG. 6) then uses theerror-corrected tier 1-encoded LSB page 1 data and the tier 1-encodedMSB page 4 data contained in the LSB and MSB page buffer portions 201 band 201 a, respectively, (FIG. 6) to determine the proper referencevoltage ranges to be programmed for the flash cells 195 connected toword line 196 b (FIG. 5).

The SSD controller 100 loads LSB pages 3 and 5 and MSB pages 6 and 8into buffer 131 (FIG. 4). The ECC module 161 (FIG. 4) uses the tier 1encoder/decoder 161 a and the tier 2 encoded/decoder 161 b to performtier 1 and tier 2 ECC encoding, respectively, on the LSB page 3 data andsends the tier 1/tier 2-encoded LSB page 3 data to the flash die 194,which loads the LSB page 3 data into the LSB page buffer portion 201 b(FIG. 6) of flash die 194. Logic (not shown) inside of the flash die 194then writes the tier 1/tier 2-encoded LSB page 3 data held in LSB pagebuffer portion 201 b (FIG. 6) to the corresponding flash cells 195 (FIG.5) connected to word line 196 c (FIG. 5).

The ECC module 161 uses the tier 1 encoder/decoder 161 a and the tier 2encoded/decoder 161 b to perform tier 1 and tier 2 ECC encoding,respectively, on the LSB page 5 data and sends the tier 1/tier 2-encodedLSB page 5 data to the flash die 194, which loads the LSB page 5 datainto the LSB page buffer portion 201 b (FIG. 6) of flash die 194,thereby overwriting the LSB page 3 data. Logic (not shown) inside of theflash die 194 then writes the LSB page 5 data to corresponding flashcells 195 connected to word line 196 d (FIG. 5).

The ECC module 161 uses the tier 1 encoder/decoder 161 a to perform tier1 ECC encoding on the MSB page 6 data. The SSD controller 100 sends thetier 1-encoded MSB page 6 data to the flash die 194, which loads the MSBpage 6 data into the MSB page buffer portion 201 a (FIG. 6) of flash die194. The tier 2 decoding logic 210 reads the tier 1/tier 2-encoded LSBpage 3 data from the LSB page of flash cells 195 (FIG. 5), performs tier2 ECC decoding on the LSB page 3 data to correct errors in the LSB page3 data, and loads the error-corrected tier 1-encoded LSB page 3 datainto the LSB page buffer portion 201 b (FIG. 6). The reference voltagedetermination logic 200 (FIG. 6) then uses the tier 1-encoded MSB page 6data and the error-corrected tier 1-encoded LSB page 3 data contained inthe MSB and LSB page buffer portions 201 a and 201 b, respectively, todetermine the proper reference voltage ranges to be programmed for theflash cells 195 connected to word line 196 c (FIG. 5).

The ECC module 161 uses the tier 1 encoder/decoder 161 a to perform tier1 ECC encoding on the MSB page 8 data and sends the tier 1-encoded MSBpage 8 data to the flash die 194. Logic inside of the flash die 194loads the tier 1-encoded MSB page 8 data into the MSB page bufferportion 201 a (FIG. 6). The tier 2 decoding logic 210 reads the tier1/tier 2-encoded LSB page 5 data from the corresponding LSB page offlash cells 195 (FIG. 5), performs tier 2 ECC decoding on the LSB page 5data to correct errors in the LSB page 5 data, and loads theerror-corrected tier 1-encoded LSB page 5 data into the LSB page bufferportion 201 b (FIG. 6). The reference voltage determination logic 200(FIG. 6) then uses the error-corrected tier 1-encoded LSB page 5 dataand the MSB page 8 data contained in the LSB and MSB page bufferportions 201 b and 201 a, respectively, (FIG. 6) to determine the properreference voltage ranges to be programmed for the flash cells 195connected to word line 196 d (FIG. 5).

It should be noted that the invention is not limited with respect to theorder in which data is transferred from the host system 102 to the SSDcontroller 100, ECC encoded in the SSD controller 100, transferred fromthe SSD controller 100 to the flash die 194, written to the flash cells195, read from the flash cells 195, decoded by the tier 2 ECC decodinglogic 210, loaded into and unloaded from the buffer portions 201 a and201 b, loaded into the reference voltage determination logic 200,transferred from the flash die 195 to the SSD controller 100, ECCdecoded in the SSD controller 100, and transferred from the SSDcontroller 100 to the host system 102. The above example assumes thatLSB pages and MSB pages are programmed in a particular order, but theinvention is not limited to the LSB and MSB pages being programmed inany particular order, as will be understood by those of skill in the artin view of the description being provided herein.

FIG. 9 illustrates a flow diagram that represents the method inaccordance with an illustrative embodiment for preventing errors fromoccurring when programming the reference voltage ranges. Data to bewritten to flash memory is received in the SSD controller 100 from thehost system 102, as indicated by block 221. Tier 1 and tier 2 ECCencoding is then performed on the LSB page data, as indicated by block223. The tier 1/tier 2-encoded LSB page data is then sent to the flashdie 194, as indicated by block 224. In the flash die 194, the tier1/tier 2-encoded LSB page data is written to the flash cells, asindicated by block 225.

In the SSD controller 100, tier 1 encoding is then performed in the MSBpage data, as indicated by block 226. The SSD controller 100 then sendsthe tier 1-encoded MSB page data to the flash die 194, as indicated byblock 227. In the flash die 194, the previously-written LSB page data isread from the flash cells and sent to the tier 2 ECC decoding logic 210of the flash die 194, as indicated by block 228. The tier 2 ECC decodinglogic 210 then performs tier 2 decoding on the LSB page data to correcterrors in the LSB page data, as indicated by block 229. Theerror-corrected LSB page data and the MSB page data are then used by thereference voltage determination logic 200 to determine the properreference voltage ranges for the flash cells 195, as indicated by block231. The flash cells 195 are then programmed with the determinedreference voltage ranges, as indicated by block 232.

It should be noted that the tier 2 ECC decoding process performed bylogic 210 is only performed when data is being written to the flashcells 195. During a normal read operation, the LSB and MSB page data aretransferred from the flash die 194 to the SSD controller 100 without anyECC decoding being performed in the flash die 194. In the case of anormal LSB page read operation, the tier 2 parity bits that wereconcatenated onto the LSB page data in the ECC module 161 are discardedfrom the LSB page read data. The ECC module 161 performs tier 1 (161 a)ECC decoding on the LSB page read data to correct errors in the LSB pagedata. In the case of a normal MSB page read operation, when the MSB pageread data is received in the SSD controller 100, the ECC module 161performs tier 1 ECC (161 a) decoding on the MSB page data to correcterrors in the MSB page data. Thus, the MSB page read operation isperformed in the known manner, whereas the LSB page read operationincludes the additional operation of discarding the tier 2 parity bitsbefore performing the tier 1 decoding operation. The tier 2 parity bitsmay be discarded in the flash die 194, in the SSD controller 100 or atany location in between the flash die 194 and the SSD controller 100.

It should be understood that the flow diagram of FIG. 9 is intended onlyto be exemplary or illustrative of the above-described method. In viewof the descriptions herein, persons skilled in the art readily will becapable of programming or configuring an SSD controller or similarsystem in any of various ways to effectuate the above-described methodand similar methods. The process represented by the blocks describedabove with regard to FIG. 9 is intended only as an example, and in otherembodiments the steps or acts described above and similar steps or actscan occur in any other suitable order or sequence. Steps or actsdescribed above can be combined with others or omitted in someembodiments. Similarly, the logic elements or components described abovewith regard to FIGS. 3-6 are intended only as examples of suitableconfigurations for performing the above-described method. Also, itshould be understood that the combination of software instructions orsimilar logic and the memory in which such software instructions orsimilar logic is stored or embodied in non-transitory form comprise a“computer-readable medium” or “computer program product” as that term isused in the patent lexicon.

It should be noted that the invention has been described with referenceto one or more exemplary embodiments for the purpose of demonstratingthe principles and concepts of the invention. The invention is notlimited to these embodiments. For example, although the above-describedexemplary embodiment relates to MLC NAND flash memory, other embodimentscan relate to TLC or any other suitable type of flash memory. As will beunderstood by persons skilled in the art, in view of the descriptionprovided herein, many variations may be made to the embodimentsdescribed herein and all such variations are within the scope of theinvention.

What is claimed is:
 1. A data storage system comprising: a host system;and a solid state drive (SSD) interfaced with the host system, the SSDincluding an SSD controller and at least one nonvolatile memory (NVM),the SSD controller including at least one SSD processor, a tier 1error-correcting code (ECC) encoder/decoder, and a tier 2 ECCencoder/decoder, wherein the NVM includes at least a first flash memoryhaving a plurality of flash memory cells, reference voltage rangedetermination logic and tier 2 ECC decoding logic, the SSD controllerreceiving write data from the host system to be programmed into flashcells of the NVM, the write data comprising at least a first mostsignificant bit (MSB) page of data and at least a first leastsignificant bit (LSB) page of data, the tier 1 ECC encoder/decoderperforming tier 1 ECC encoding of the first LSB page of data to producea tier 1-encoded first LSB page of data, the tier 2 ECC encoder/decoderperforming tier 2 ECC encoding of the tier 1-encoded first LSB page ofdata to produce a tier 1/tier 2-encoded first LSB page data, the SSDcontroller sending the tier 1/tier 2-encoded first LSB page of data tothe first flash memory, the tier 1 ECC encoding/decoding logicperforming tier 1 ECC encoding of the first MSB page of data to producea tier 1-encoded first MSB page of data, the SSD controller sending thetier 1-encoded first MSB page of data to the first flash memory, thetier 1 ECC encoding and the tier 2 encoding being different types ofencoding, the tier 2 decoding logic of the first flash memory beingadapted to perform tier 2 decoding of LSB page data in the first flashmemory.
 2. The data storage system of claim 1, wherein the first flashmemory receives the tier 1/tier 2-encoded first LSB page of data andwrites the tier 1/tier 2-encoded first LSB page of data to a first LSBpage of the flash memory cells, and wherein the first flash memoryreceives the tier 1-encoded first MSB page of data, the first flashmemory reading the tier 1/tier 2-encoded first LSB page of data from thefirst LSB page of the flash memory cells and sending the read tier1/tier 2-encoded first LSB page to the tier 2 ECC decoding logic of thefirst flash memory, the tier 2 ECC decoding logic performing tier 2 ECCdecoding on the tier 1/tier 2-encoded first LSB page of data to producean error-corrected tier 1-encoded first LSB page of data, the referencevoltage range determination logic using the error-corrected tier1-encoded first LSB page of data and the tier 1-encoded first MSB pageof data to determine reference voltage ranges for a first MSB page ofthe flash memory cells of the first flash memory, and wherein the firstflash memory programs the determined reference voltage ranges into thefirst flash memory and writes the tier 1-encoded first MSB page of datato the first MSB page of the flash memory cells.
 3. The data storagesystem of claim 2, wherein the tier 1 ECC encoding performed by the tier1 ECC encoder/decoder of the SSD controller is soft-decision ECCencoding and wherein the tier 2 encoding performed by the tier 2 ECCencoder/decoder of the SSD controller is hard-decision ECC encoding, andwherein the tier 2 ECC decoding logic of the first flash memory performshard-decision ECC decoding.
 4. The data storage system of claim 2,wherein during a normal LSB page read operation, the first flash memoryreads the tier 1/tier 2-encoded first LSB page of data from the firstLSB page of the flash memory cells of the first flash memory, discardstier 2 parity bits from the first LSB of read data to remove tier 2decoding of the first LSB page of read data, and sends a tier 1-encodedfirst LSB page of read data to the SSD controller without the tier 2 ECCdecoding logic of the first flash memory performing tier 2 ECC decodingof the tier 1/tier 2-encoded first LSB page of read data.
 5. The datastorage system of claim 4, wherein the tier 1-encoded first LSB page ofread data that is sent from the first flash memory to the SSD controlleris decoded by the tier 1 ECC encoder/decoder of the SSD controller toproduce a tier1-decoded first LSB page of read data.
 6. The data storagesystem of claim 5, wherein during a normal MSB page read operation, thefirst flash memory causes the tier 1-encoded first MSB page of data tobe read from the first MSB page of the flash memory cells and sent tothe SSD controller, and wherein the tier 1-encoded first MSB page ofread data that is sent from the first flash memory to the SSD controlleris decoded by the tier 1 ECC encoder/decoder of the SSD controller toproduce a tier1-decoded first MSB page of read data.
 7. The data storagesystem of claim 1, wherein the first flash memory is disposed in a firstintegrated circuit (IC) die and wherein the SSD controller is disposedon a second IC that is interfaced with the first IC to enable the firstand second ICs to communicate with one another.
 8. A first flash memoryintegrated circuit (IC) die for use in a solid state drive (SSD) of adata storage system, the first flash memory IC die comprising: aplurality of flash memory cells for storing data; error-correcting code(ECC) decoding logic, the first flash memory IC die being configured toreceive write data from an interface that interfaces an SSD controllerof the SSD with the first flash memory IC die, the received write datacomprising at least a first least significant bit (LSB) page of data andat least a first most significant bit (MSB) page of data, the first LSBpage of data being encoded with a tier 1 ECC encoding and with a tier 2ECC encoding, the first MSB page of data being encoded with the tier 1encoding, the first flash memory IC die programming the first LSB pageof data to a first LSB page of the flash memory cells, wherein prior tothe first flash memory IC die programming the first MSB page of data toa first MSB page of the flash memory cells, the first flash memory ICdie causes the encoded first LSB page of data to be read from the firstLSB page of the flash memory cells and sent to the ECC decoding logic,and wherein the ECC decoding logic performs tier 2 ECC decoding of theencoded LSB page data to produce a tier 2-decoded first LSB page ofdata.
 9. The first flash memory IC die of claim 8, further comprising:reference voltage range determination logic for determining referencevoltage ranges to be programmed into the flash cells, the referencevoltage range determination logic using the tier 2-decoded first LSBpage of data and the tier 1-encoded first MSB page of data to determinereference voltage ranges to be programmed for the first MSB page offlash memory cells.
 10. The first flash memory die of claim 9, whereinthe tier 1 ECC encoding is soft-decision ECC encoding and wherein thetier 2 encoding is hard-decision ECC encoding, and wherein the ECCdecoding logic of the first flash memory IC die performs hard-decisionECC decoding.
 11. The first flash memory IC die of claim 8, whereinduring a normal LSB page read operation, the first flash memory IC diereads the tier 1/tier 2-encoded first LSB page of data from the firstLSB page of the flash memory cells, discards tier 2 parity bits from thefirst LSB of read data to remove tier 2 decoding of the first LSB pageof read data, and sends a tier 1-encoded first LSB page of read data tothe interface without the ECC decoding logic of the first flash memoryIC die performing tier 2 ECC decoding of the tier 1/tier 2-encoded firstLSB page of data.
 12. A method for programming data to flash memory of adata storage system, the method comprising: in a solid state drive (SSD)interfaced with a host system, receiving write data to be written to atleast one nonvolatile memory (NVM), the write data comprising at least afirst most significant bit (MSB) page of data and at least a first leastsignificant bit (LSB) page of data, wherein the NVM includes at least afirst flash memory having a plurality of flash memory cells, referencevoltage range determination logic and tier 2 ECC decoding logic; in anSSD controller of the SSD, receiving the write data to be written to theNVM, the SSD controller including at least one SSD processor, tier 1error-correcting code (ECC) encoder/decoder, and tier 2 ECCencoder/decoder; in the tier 1 ECC encoder/decoder, performing tier 1ECC encoding of the first LSB page of data to produce a tier 1-encodedfirst LSB page of data; in the tier 2 ECC encoder/decoder, performingtier 2 ECC encoding of the tier 1-encoded first LSB page of data toproduce a tier 1/tier 2-encoded first LSB page data; in the SSDcontroller, sending the tier 1/tier 2-encoded first LSB page of data tothe first flash memory; in the tier 1 ECC encoder/decoder, performingtier 1 ECC encoding of the first MSB page of data to produce a tier1-encoded first MSB page of data; and in the SSD controller, sending thetier 1-encoded first MSB page of data to the first flash memory, thetier 1 ECC encoding and the tier 2 encoding being different types ofencoding.
 13. The method of claim 12, further comprising: in the firstflash memory, receiving the tier 1/tier 2-encoded first LSB page ofdata; in the first flash memory, programming the tier 1/tier 2-encodedfirst LSB page of data to a first LSB page of the flash memory cells; inthe first flash memory, receiving the tier 1-encoded first MSB page ofdata; in the tier 2 decoding logic of the first flash memory, performingtier 2 decoding of the tier 1/tier 2-encoded first LSB page of data thatwas programmed to the first LSB page of flash memory cells to produce atier 2-decoded first LSB page of data; and in the reference voltagerange determination logic, prior to programming the tier 1-encoded firstMSB page of data to a first MSB page of flash memory cells, using thetier 1-encoded first MSB page of data and the tier 2-decoded first LSBpage of data to determine reference voltage ranges for the first MSBpage of flash memory cells.
 14. The method of claim 13, furthercomprising: after determining the reference voltage ranges, programmingthe determined reference voltage ranges into the first MSB page of flashmemory cells.
 15. The method of claim 13, further comprising: prior toprogramming the tier 1/tier 2-encoded first LSB page of data to thefirst LSB page of the flash memory cells, buffering the tier 1/tier2-encoded first LSB page of data in a LSB page buffer portion of abuffer of the first flash memory; and after programming the tier 1/tier2-encoded first LSB page of data to the first LSB page of the flashmemory cells, buffering the tier 1-encoded first MSB page of data in anMSB page buffer portion of the buffer of the first flash memory.
 16. Themethod of claim 15, further comprising: after performing tier 2 decodingof the tier 1/tier 2-encoded first LSB page of data and prior todetermining the reference voltage ranges: loading the tier 2-decodedfirst LSB page of data into the LSB page buffer portion; moving the tier2-decoded first LSB page of data and the tier 1-encoded first MSB pageof data from the LSB and MSB page buffer portions, respectively, to thereference voltage range determination logic.
 17. The method of claim 14,wherein the tier 1 ECC encoding performed by the tier 1 ECCencoder/decoder of the SSD controller is soft-decision ECC encoding andwherein the tier 2 encoding performed by the tier 2 ECC encoder/decoderof the SSD controller is hard-decision ECC encoding, and wherein thetier 2 ECC decoding logic of the first flash memory performshard-decision ECC decoding.
 18. The method of claim 13, furthercomprising: during a normal LSB page read operation, the first flashmemory reading the tier 1/tier 2-encoded first LSB page of data from thefirst LSB page of the flash memory cells of the first flash memory,discarding tier 2 parity bits from the first LSB of read data to removetier 2 decoding of the first LSB page of read data, and sending a tier1-encoded first LSB page of read data to the SSD controller without thetier 2 ECC decoding logic of the first flash memory performing tier 2ECC decoding of the tier 1/tier 2-encoded first LSB page of read data.19. The method of claim 18, further comprising: in the SSD controller,receiving the tier 1-encoded first LSB page of read data sent from thefirst flash memory to the SSD controller; in the tier 1 ECCencoder/decoder of the SSD controller, decoding the tier 1-encoded firstLSB page of read data to produce a tier1-decoded first LSB page of readdata.
 20. The method of claim 19, further comprising: during a normalMSB page read operation, the first flash memory causing the tier1-encoded first MSB page of data to be read from the first MSB page ofthe flash memory cells of the first flash memory and sent to the SSDcontroller.
 21. The method of claim 20, further comprising: in the SSDcontroller, receiving the tier 1-encoded first MSB page of read datasent from the first flash memory to the SSD controller; and in the tier1 ECC encoder/decoder of the SSD controller, decoding the tier 1-encodedfirst MSB page of read data to produce a tier1-decoded first MSB page ofread data.